Switch to GitHub issue forms#7773
Conversation
|
Is it okay even if they're still in beta? I know the Matrix/Element teams use them for all their repos. |
|
The dumdum CI shouldn't run when non-code files are modified. |
|
Please feel free to take some inspiration from https://github.com/TheAssassin/AppImageLauncher/tree/master/.github/ISSUE_TEMPLATE. I think you mostly converted the existing template, but there is some potential for improvements. I'll leave a review shortly. |
TheAssassin
left a comment
There was a problem hiding this comment.
I reviewed one of them now, but most of my feedback applies to all three.
4795961 to
c7ff214
Compare
c7ff214 to
b61e6f6
Compare
Credits to @TheAssassin
|
@TheAssassin |
opusforlife2
left a comment
There was a problem hiding this comment.
I love it. This is so much better than letting users manually fiddle with Markdown.
Credits to @opusforlife2
|
@opusforlife2 |
|
@mhmdanas |
|
Kudos, SonarCloud Quality Gate passed! |
|
Thanks, litetex! |









What is it?
Description of the changes in your PR
This is a first step/try to stop issue spamming by users which are unable to read the template/delete it.
Backstory: We got ~30 issue duplicates in one day despite having a pinned issue (→ #7734)
This switches our issue templates to GitHub issue form(s)-templates (still in beta) which should be more intuitive for users to fill out.
This is also a preparation for #6941
See also
Before/After Screenshots/Screen Record
→ Live demo: https://github.com/litetex/np-gh-issue-forms/issues/new/choose
Due diligence